Alphanumeric Address Mapping for Non-Homogeneous Short Message Networks

ABSTRACT

Text messages with alphanumeric addresses are delivered to mobiles and external short message entities (ESMEs) which do not support alphanumeric addressing, providing meaningful fallback handling. Additionally, the invention enables delivery of SMPP messages from ESME or SMPP networks which can only originate numeric addresses, yet provide for mapping to alphanumeric addresses for delivery to the mobile. A two-way mapping is provided between alphanumeric addresses and SMS short-codes to enable delivery of text messages with alphanumeric addressing in networks which contain mobiles and/or ESME&#39;s that lack support of alphanumeric addressing. 
     An ESME can send a text message using an alphanumeric origination address, without knowing which handsets support the capability, and which do not, or whether handsets are on CDMA, or GSM, or UMTS, or long term evolution (LTE) networks, or can continue to send using a numeric origination address. The SMSC provides conversions to alphanumeric addresses on behalf of the ESME and the mobile.

This application claims priority from U.S. Provisional No. 61/457,084,entitled “ALPHANUMERIC ADDRESS MAPPING FOR NON-HOMOGENEOUS SHORT MESSAGENETWORKS” to Paul CASTO, Lewis TUTTLE, and Donghong GAO, filed Dec. 23,2010, the entirety of which is expressly incorporated herein byreference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to telecommunications, Moreparticularly, it relates to wireless based technologies.

2. Background of the Related Art

When a short message service center (SMSC) operates in a long termevolution (LTE)/CDMA (or GSM/CDMA, or UMTS/CDMA) dual mode network, thevast majority of GSM, UMTS and LTE mobiles support alphanumericaddressing where as many or most CDMA mobiles may not. This impacts thedisplay of the originator of the message to the end-user of the mobilephone (or conversely the terminator, when the user is replying). Manycorporations would like messages that they send to an end-user to appearwith some form of corporate branding. E.g. ABXCorp would rather have theend user see a message from ABXCorp, rather than see that they have amessage from 12345, and then have to figure out what those numbersrepresent.

A similar issue is also found in supporting external short messageentities (ESMEs) from two different vendors. Some ESMEs supportalphanumeric addressing while others do not.

Currently, if the mobile or ESME does not allow for message deliverywith alphanumeric addresses encoded, the message to the mobile or theESME may be discarded.

Alternatively, for messages destined to a Mobile, a generic numericaladdress may be substituted for the alphanumeric address, but asubstituted generic numerical address is not meaningful to the Mobileend-user.

Many GSM/UMTS/LTE handsets support alphanumeric addresses. Some CDMAhandsets may support alphanumeric (IA5) addresses. SMPP standardsupports alphanumeric addresses, but many ESMEs/SMPP gateways have notfully implanted that portion of the standard. Thus, while end-points(some handsets and some ESMEs) may support alphanumeric addressing, thesupport for end-to-end alphanumeric addressing is not always complete.ESMEs that are aware that a particular end-user handset has thealphanumeric capability could attempt delivery using that format, butthat would require the ESME to maintain information about every phonenumber that it is sending to. Moreover, an ESME maintaining informationabout every phone number that it is sending to would be very susceptibleto the user changing handset models.

Messages that are deleted due to protocol errors (e.g. handset cannotdecode an address with alphanumeric characters) result in non-deliveryto the subscriber. Messages that have had generic ‘alphanumeric togeneric’ translation rules applied arrive at the handset withoutallowing the handset device to obtain the identity of the originator,thus also preventing the user device from responding.

SUMMARY OF THE INVENTION

In accordance with the principles of the present invention, a method ofhandling alphanumeric address mapping for a non-homogeneous shortmessage network comprises receiving a message including an alphanumericorigination address, from an external short message entity (ESME),destined for a terminating mobile device. Mapping the alphanumericorigination address identifying the originating sender's address to adigit string identifying the originating sender's address prior to thefirst attempt to deliver the message to the terminating mobile device.The message is then routed to a terminating mobile device includingnumeric destination addressing.

A method of handling alphanumeric address mapping for a non-homogeneousshort message network in accordance with another embodiment of theinvention comprises receiving a message including an alphanumericorigination address identifying an originating sender from an externalshort message entity (ESME). The message is routed to a terminatingmobile device including alphanumeric origination addressing. A faileddelivery message relating to failure of the message is received. Thealphanumeric origination address identifying the originating sender ismapped to a digit string that provides an alternative identification ofthe originating sender. The message is routed to the terminating mobiledevice including numeric destination addressing. This provides supportfor the use cases where the originating ESMEs (and interveninginfrastructure) provides the capability to originate messages fromalphanumeric addresses, but the receiving devices include a range ofnetwork types (LTE/CDMA/UMTS/GSM) and handset types, some of which dosupport receiving these messages, others of which can not.

Yet another embodiment of the invention discloses a method of handlingalphanumeric address mapping for a non-homogeneous short messagenetwork. A message is received including a numeric originationaddressidentifying the originating senderfrom an external short messageentity (ESME). The numeric origination address identifying the theoriginating sender is mapped to an alphanumeric string identifying thean alphanumeric address for the originating sender, prior to a firstattempt to deliver the message to the terminating mobile device. Themessage is routed to a terminating mobile device including alphanumericoriginating address. This provides support for the use cases where theoriginating ESMEs (or intervening infrastructure) lacks the capabilityto originate messages addressed from an alphanumeric address, yet some,or all of the handsets (and supporting infrastructure) has thecapability to receive such messages. A further fallback to the firstembodiment is also possible in this case.

Still another embodiment discloses a method of handling alphanumericaddress mapping for a non-homogeneous short message network. A messageis received including an alphanumeric destination address identifying aterminating external short message entity (ESME), from a mobile device.It is determined through configuration that the terminating externalshort message entity (ESME) requires numeric addressing. Thealphanumeric destination address is converted to a digit address. Themessage addressed with the digit address is routed to the external shortmessage entity (ESME). This provides support for the use cases where theoriginating handsets (and intervening infrastructure) provide thecapability to originate messages addressed to an alphanumeric ESMEaddress (including the case of ‘reply to’ alphanumeric addresses), butthe ESME (or intervening infrastructure) lacks the capability to receivesuch messages.

BRIEF DESCRIPTION OF THE DRAWINGS

Features and advantages of the present invention become apparent tothose skilled in the art from the following description with referenceto the drawings:

FIG. 1 shows call flow from an alphanumeric addressing external shortmessage entity (ESME) to a numeric addressing mobile device, fornon-homogeneous short message networks, in accordance with theprinciples of the present invention.

FIG. 2 shows another exemplary call flow from an alphanumeric addressingexternal short message entity (ESME) to a numeric addressing mobiledevice, for non-homogeneous short message networks, in accordance withthe principles of the present invention.

FIG. 3 shows call flow from a numeric addressing external short messageentity (ESME) to an alphanumeric addressing mobile device, fornon-homogeneous short message networks, in accordance with theprinciples of the present invention.

FIG. 4 shows call flow from an alphanumeric addressing mobile device toa numeric addressing external short message entity (ESME), fornon-homogeneous short message networks, in accordance with theprinciples of the present invention.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present invention delivers text messages with alphanumeric addressesto mobile devices and external short message entities (ESMEs) which donot support alphanumeric addressing, and provides meaningful fallbackhandling.

Additionally, the invention enables delivery of Short Message Peer toPeer (SMPP) messages from ESMEs or SMPP networks which can onlyoriginate numeric addresses, yet provide for mapping to alphanumericaddresses for delivery to a destination wireless mobile device.

The present invention adapts technology which is available withinvarious telecommunication standards, but under-used due to thechallenges of interoperability in heterogeneous networks. The inventivesolution provides a two-way mapping between alphanumeric addresses andshort message system (SMS) short-codes to enable delivery of textmessages with alphanumeric addressing in networks which contain mobilesand/or ESME's that lack support of alphanumeric addressing.

In accordance with the invention, an ESME can send a text message usingan alphanumeric origination address, without the need to know whichhandsets support the capability, and which do not, or whether handsetsare on CDMA, or GSM, or UMTS, or long term evolution (LTE) networks, orcan continue to send using a numeric origination address, The ShortMessage Servicing Center (SMSC) provides conversions to alphanumericaddresses on behalf of the ESME and mobile device.

This supports mapping of source and originating addresses both from andto numeric addresses, and mapping of numeric source addresses toalphanumeric for ESME_>Mobile Terminated call flows.

The configuration of the mapping is preferably accomplished such thatthe number is a meaningful representation of the alphanumeric address.For example, if ABXCorp's short-code address is “12345”, messages withan originating address of “ABXCorp” will fall back to “12345”. In thismanner, response messages addressed to either “ABXCorp” or “12345” arerouted to the same destination ESME.

As an extension, or alternate to, the static mapping approach, ESMEs mayalso include a custom Tag Length Value (TLV) component of an SMPPmessage to provide an alternate origination address. This allows ESMEsto provide address information in a dynamic fashion, without need forprovisioning of a translation table at the SMSC, and still overcomescases where the infrastructure between the ESME and the SMSC does notsupport use of alphanumeric addresses directly.

Messages which fail to be delivered due to protocol errors, system orinterface configuration, preferably trigger the SMSC 120 to convert thealphanumeric origination address to a meaningful numeric originationaddress.

In addition to per-message support, entire air-interfaces may beconfigured to convert alphanumeric addresses back to numeric.

For ESMEs connected to a specific port, the connection may be configuredto convert addresses to numbers when alphanumeric addresses are notsupported. ESMEs can also be configured by system-type to identify thosewhich cannot support alphanumeric addressing. Or by alphanumeric name(e.g,, messages to “ABXCorp” always get converted to “12345”).

The present invention provides focus on four primary call flows shown inFIGS. 1 through 4.

FIG. 1 shows call flow from an alphanumeric addressing external shortmessage entity (ESME) to a numeric addressing mobile device, fornon-homogeneous short message networks, in accordance with theprinciples of the present invention.

In particular, as shown in the call flow of FIG. 1, a message originatesfrom an external short message entity (ESME) with an alphanumericoriginating address, and terminates to a mobile device where the ESMEdoes not support alphanumeric addressing. These may be addressed in twoways, shown in FIG. 1 and FIG. 2.

With respect to FIG. 1, the air interface (such as CDMA) may beconfigured not to support alphanumeric addressing. This causes themessage's alphanumeric origination address to be mapped to a digitstring, prior to the first attempt. The second technique (shown in FIG.2) permits the message to fail delivery based on a failure response(such as protocol error), at which time, the SMSC then maps thealphanumeric origination address to a number and retries delivery of themessage.

As shown in FIG. 1, an exemplary call flow is described between anoriginating mobile device 110 (e.g., a CDMNGSM/UMTS/LTE mobile), a shortmessage service center (SMSC) 120, a prepaid server 130, and a receivingexternal short message entity (ESME) 140.

The ESME 140 sends a Submit SM message 310 including alphanumericoriginating address to the SMSC 120.

As depicted in module 320, the prepaid server 130 is configured fornumeric addressing only.

In step 340, an alphanumeric originating address is mapped to a uniquenumeric value. The SMSC 120 sends a Debit request message 350 withnumeric originating address to the prepaid server 130.

The prepaid server 130 sends a Debit Response message 360 back to theSMSC 120, which sends a Submit SM Response message 330 to the ESME 140.

In step 370 the CDMA or GSM network, or per-subscriber, is configured toconvert alphanumeric addresses prior to delivery.

The alphanumeric originating address is mapped to a unique numeric valuein step 372.

The SMSC 120 sends a Delivery Attempt message with numeric originatingaddress 374 to the CDMA or GSM or IMS or LTE mobile device 110, whichsends back a Delivery Attempt message 376 with results.

In step 378, the SMSC 120 configures the billing/call detail records fora numeric address.

In step 380, the alphanumeric originating address is mapped to a uniquenumeric value.

In step 382, the billing/call detailed record is written with a numericorigination address.

FIG. 2 shows another exemplary call flow from an alphanumeric addressingexternal short message entity (ESME) to a numeric addressing mobiledevice, for non-homogeneous short message networks, in accordance withthe principles of the present invention.

In particular, as shown in FIG. 2, the ESME 140 sends a Submit_SMmessage 410 including alphanumeric originating address to the SMSC 120.

As depicted in module 420, the prepaid server 130 is configured fornumeric addressing only.

In step 440, an alphanumeric originating address is mapped to a uniquenumeric value. The SMSC 120 sends a Debit request message 450 withnumeric originating address to the prepaid server 130.

The prepaid server 130 sends a Debit Response message 460 back to theSMSC 120, which sends a Submit_SM Response message 430 to the ESME 140.

The SMSC 120 sends a Delivery Attempt with alphanumeric originatingaddress to the mobile device 110 (e.g., a CDMA, GSM, IMS or LTE mobiledevice).

In response, a Delivery Attempt Failure message 480 with protocol erroris sent from the mobile device 110 back to the SMSC 120.

In step 482, it is determined that the message containing analphanumeric address failed with a protocol error.

In step 484 the alphanumeric originating address is mapped to a uniquenumeric value.

A Delivery Attempt message 486 with numeric originating address is sentto the mobile device 110, which sends back a Delivery Attempt Successmessage 488.

In step 490, billing/call detail records are configured for numericaddress.

In step 492, the alphanumeric originating address is mapped to a uniquenumeric value.

In step 494, the billing/call detailed record is written with a numericorigination address.

FIG. 3 shows call flow from a numeric addressing external short messageentity (ESME) to an alphanumeric addressing mobile device, fornon-homogeneous short message networks, in accordance with theprinciples of the present invention.

In particular, in the call flow of FIG. 3, a message originates from anESME terminating to a mobile device where the ESME sends a numericaddress (but would prefer an alphanumeric address be used wherepossible). This call flow encompasses messages originating from an ESMEwith numeric originating addresses, and terminating to a mobile whichmay support alphanumeric addressing (based on per-interface or persubscriber rules). This causes the message's numeric origination addressto be mapped to an alphanumeric string, prior to the first attempt.Should an attempt fail, due to protocol error, the fallback mappingoccurs as with respect to the call flow of FIGS. 1 and 2.

As shown in FIG. 3, the ESME 140 sends a Submit_SM message 510 includinga numeric originating address to the SMSC 120.

The SMSC 120 sends a Debit Request message 520 with numeric originatingaddress to the prepaid server 130, which sends a Debit Response message540 back to the SMSC 120,

The SMSC 120 sends a Submit_SM Response message 530 to the ESME 140.

In step 550, the LTE, CDMA, UMTS, or GSM network, or per-subscriber, isconfigured to convert alphanumeric addresses prior to delivery.

In step 560 the numeric originating address is mapped to a uniquealphanumeric value.

The SMSC 120 sends a Delivery Attempt with alphanumeric originatingaddress message 570 to the mobile device 110 (e.g., a CDMA, GSM, UMTS orLTE mobile device).

In response, a Delivery Attempt results message 580 is sent from themobile device 110 back to the SMSC 120.

In step 582, it is determined that the delivery attempt failed with aprotocol error.

In step 584 the alphanumeric originating address is mapped back to theoriginal numeric value.

A Delivery Attempt message 586 with numeric originating address is sentto the mobile device 110, which sends back a Delivery Attempt resultsmessage 588.

In step 590, the billing/call detail records are written with a numericorigination address.

FIG. 4 shows call flow from an alphanumeric addressing mobile device toa numeric addressing external short message entity (ESME), fornon-homogeneous short message networks, in accordance with theprinciples of the present invention.

In particular, in the call flow of FIG. 4, a message originates from amobile device with an alphanumeric destination address, and terminatesto an ESME that does not support alphanumeric addressing. In this case,based on ESME configuration provisioning, the SMSC converts thealphanumeric destination address to a digit address and sends the textmessage to the ESME. Since ESMEs are relatively static, the requirementto convert is normally accomplished through configuration. While theinvention encompasses a possible attempt followed by a retry, this isinefficient for the mobile originated (MO) to ESME case.

As shown in FIG. 4, the short message service center 120 receives aSubmit_SM type message 210 from the originating mobile device 110,including an alphanumeric destination address.

A prepaid/usage control module 150 in the SMSC 120 receives theSubmit_SM message 210, and the prepaid/usage control module 150 isconfigured for numeric address only.

In step 160, the alphanumeric destination address is mapped to a uniquenumeric value 160 within an appropriate module at the SMSC 120.

In message 215, a Debit request with numeric destination address is sentfrom the SMSC 120 to a prepaid module 130. The prepaid module 130returns a Debit Response to the SMSC 120, and a Submit_SM Response ispassed from the SMSC 120 to the originating mobile device 110.

In step 170, the SMSC 120 determines that the ESME 140 is configured toaccept numeric values only, so there is a need to convert alphanumericaddresses to numeric value.

In step 180 an alphanumeric destination address is mapped to a uniquenumeric value.

In message 240 a Submit_SM with numeric destination address is sent fromthe SMSC 120 to the external short message entity (ESME) 140.

In message 250 the ESME 140 sends a Submit_SM with response back to theSMSC 120.

In step 190 the billing/call detail records configured for numericaddress.

In step 200 the alphanumeric destination address is mapped to a uniquenumeric value.

In step 210 the billing/call detailed record written with numericdestination address.

There are numerous extensions envisioned within the scope of theprinciples of the present invention. For instance:

Tracking and retaining the handsets capabilities for a period of time.In this way, if an alphanumeric fails, subsequent messages areautomatically converted, prior to the first attempt.

Configuring per-subscriber exceptions to the per-air-interface rules.This accommodates gradual adoption of handsets—particularly in the CDMAenvironment which supports IA5 encoding.

The present invention provides an SMSC module that provides a bridgebetween systems which have the capability to support addressing betweenwireless devices that may or may not be capable of dealing withalphanumeric addresses.

The present invention permits ESMEs to support a branded source toclearly identify the originator, e.g., a message from “ABXCorp” or amessage from “12345”—Many vendors much prefer to put their brand name infront of a customer, rather than a short code,

The present invention has particular applicability to wireless carriermarkets, e.g, to carriers having mixed LTE/CDMA or GSM/CDMA or UMTS/CDMAnetworks. The invention may be implemented in an SMSC that supports dualnetworks (e.g., CDMA network LTE or GSM) where handsets receive textmessages from ESMEs that show an originating alphanumeric address.

While prepaid debit is shown with respect to the embodiments of thepresent invention, the invention applies equally to post-paidembodiments.

While the invention has been described with reference to the exemplaryembodiments thereof, those skilled in the art will be able to makevarious modifications to the described embodiments of the inventionwithout departing from the true spirit and scope of the invention.

1-10. (canceled)
 11. A method of providing two-way alphanumeric addressmapping for a non-homogeneous text message network, comprising:receiving a text message including an alphanumeric destination addressincluding at least one non-numeric character, said alphanumericdestination address identifying a destination mobile device; mapping,prior to a first attempt to deliver said text message to saiddestination mobile device, said alphanumeric destination addressincluding said at least one non-numeric character, to a numericdigit-only short code associated with said destination mobile device;routing said text message with said numeric digit-only short codeaddressing to said destination mobile device; receiving from saiddestination mobile device, a return text message including a numericdigit-only short code address identifying an originating mobile device;mapping said numeric digit-only short code address of said return textmessage to an alphanumeric originating address including at least onenon-numeric character corresponding to said originating mobile device;and routing said return text message to said originating mobile device.12. A method of providing two-way alphanumeric address mapping for anon-homogeneous text message network according to claim 11, wherein saiddestination mobile device comprises: an external short message entity(ESME).
 13. A method of providing two-way alphanumeric address mappingfor a non-homogeneous text message network according to claim 12,wherein said text message comprises: a short message system (SMS) textmessage.
 14. A method of providing two-way alphanumeric address mappingfor a non-homogeneous text message network according to claim 11,wherein said originating mobile device comprises: an external shortmessage entity (ESME).
 15. A method of providing two-way alphanumericaddress mapping for a non-homogeneous text message network according toclaim 14, wherein said text message comprises: a short message system(SMS) text message.
 16. A method of providing two-way alphanumericaddress mapping for a non-homogeneous text message network according toclaim 11, wherein said text message comprises: a short message system(SMS) text message.
 17. The method of providing two-way alphanumericaddress mapping for a non-homogeneous text message network according toclaim 11, wherein: said originating mobile device is configured to senda text message using an alphanumeric address, irrespective of acapability of said destination mobile device to support alphanumericaddressing, and irrespective of a network type of said destinationmobile device.
 18. A method of providing two-way alphanumeric addressmapping for a non-homogeneous text message network, comprising:receiving a text message including an alphanumeric destination addressincluding at least one non-numeric character, said alphanumericdestination address identifying a destination mobile device; routingsaid text message to said destination mobile device with saidalphanumeric origination address including at least one non-numericcharacter; receiving a failed delivery message relating to failure ofdelivery of said text message to said destination mobile device; mappingsaid alphanumeric destination address including at least one non-numericcharacter, to a numeric digit-only short code string associated withsaid destination mobile device; and routing said text message with saidnumeric digit-only short code addressing to said destination mobiledevice.
 19. A method of providing two-way alphanumeric address mappingfor a non-homogeneous text message network according to claim 18,wherein said destination mobile device comprises: an external shortmessage entity (ESME).
 20. A method of providing two-way alphanumericaddress mapping for a non-homogeneous text message network according toclaim 19, wherein said text message comprises: a short message system(SMS) text message.
 21. A method of providing two-way alphanumericaddress mapping for a non-homogeneous text message network according toclaim 18, wherein said text message comprises: a short message system(SMS) text message.
 22. The method of providing two-way alphanumericaddress mapping for a non-homogeneous text message network according toclaim 16, wherein: said text message is originated by an originatingmobile device; and said originating mobile device is configured to sendtext messages using an alphanumeric origination address, irrespective ofa capability of said destination mobile device to support alphanumericaddressing, and irrespective of a network type of said destinationmobile device.